Vehicle data management device, vehicle data management system, and method of managing vehicle data

ABSTRACT

A vehicle data management device includes a data acquisition unit and a data conversion unit. The data acquisition unit is configured to acquire, from each of a plurality of in-vehicle devices mounted on a corresponding vehicle of a plurality of vehicles, a vehicle identification information that is set based on at least a model of the vehicle, and a first data that is contained in a communication frame and is indicative of a vehicle information. The data conversion unit is configured to convert the first data into a label and a second data based on a conversion map that contains a label identification information for identifying the label corresponding to the first data, and a conversion information for converting the first data into the second data. The conversion map contains at least one label identification information and at least one conversion information for each vehicle identification information.

CROSS REFERENCE TO RELATED APPLICATION

This application is based on and incorporates herein by referenceJapanese Patent Application No. 2020-035755 filed on Mar. 3, 2020.

TECHNICAL FIELD

The present disclosure relates to a vehicle data management device, avehicle data management system, and a method of managing vehicle data.

BACKGROUND

A remote data collection system for getting vehicle data into a centerthrough wireless communication is known.

SUMMARY

When the vehicle data acquired through the wireless communication isaccumulated as it is, different identification numbers may be added tothe vehicle data of the same type (e.g. vehicle speed data, engine speeddata) due to the differences between the specifications of the vehiclemodels or the vehicle manufacturers, and accordingly the data may betreated as data of different types.

When the vehicle data is collected from vehicles on the scale ofmillions to tens of millions, the data collection target vehicles varyin specification, the year model, the manufacturer, and the like.Accordingly, if the vehicle data is classified based on thespecifications, the model year, and the like, the database may becomecomplicated, and the vehicle data of the same type may not be treated asthe same type data.

A vehicle data management device according to a first aspect includes adata acquisition unit and a data conversion unit. The data acquisitionunit is configured to acquire, from each of a plurality of in-vehicledevices mounted on a corresponding vehicle of a plurality of vehicles, avehicle identification information that is set based on at least a modelof the vehicle, and a first data that is contained in a communicationframe transmitted and received in an in-vehicle network of the vehicleand is indicative of a vehicle information relating to the vehicle. Thedata conversion unit is configured to convert the first data into alabel and a second data that is a physical value or a type value basedon a conversion map that contains a label identification information foridentifying the label corresponding to the first data, and a conversioninformation for converting the first data into the second data. Theconversion map contains at least one label identification informationand at least one conversion information for each vehicle identificationinformation.

A vehicle data management system according to a second aspect includes avehicle data management device, at least one map storage device, and ananalysis device. The data acquisition unit is configured to acquire,from each of a plurality of in-vehicle devices mounted on acorresponding vehicle of a plurality of vehicles, a vehicleidentification information that is set based on at least a model of thevehicle, and a first data that is contained in a communication frametransmitted and received in an in-vehicle network of the vehicle and isindicative of a vehicle information relating to the vehicle. The dataconversion unit is configured to convert the first data into a label anda second data that is a physical value or a type value based on aconversion map that contains a label identification information foridentifying the label corresponding to the first data, and a conversioninformation for converting the first data into the second data. Theconversion map contains at least one label identification informationand at least one conversion information for each vehicle identificationinformation. The at least one map storage device stores the conversionmap. The analysis deice is configured to analyze the vehicle using thelabel and the second data converted by the vehicle data managementdevice. The at least one map storage device and the vehicle datamanagement device are communicably connected with each other.

According to a third aspect, a method of managing vehicle data includes:acquiring a vehicle identification information and a first data fromeach of a plurality of in-vehicle devices mounted on a correspondingvehicle of a plurality of vehicles, the vehicle identificationinformation being set based on at least a model of the vehicle, thefirst data being indicative of a vehicle information relating to thevehicle and being contained in a communication frame transmitted andreceived in an in-vehicle network of the vehicle; and converting thefirst data into a label and a second data that is a physical value or atype value based on a conversion map that contains a labelidentification information for identifying the label corresponding tothe first data and a conversion information for converting the firstdata into the second data, the conversion map containing at least onelabel identification information and at least one conversion informationfor each vehicle identification information.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating a vehicle data management system.

FIG. 2 is a block diagram illustrating a data collection device andmultiple ECUs mounted in a vehicle manufactured by a first vehiclemanufacturer.

FIG. 3 is a block diagram illustrating a data collection device andmultiple ECUs mounted in a vehicle manufactured by a second vehiclemanufacturer.

FIG. 4 is a block diagram illustrating a vehicle data management device.

FIG. 5 is a diagram illustrating a configuration of a frame.

FIG. 6 is a diagram illustrating a pre-conversion database.

FIG. 7 is a flowchart illustrating a data conversion process.

FIG. 8 is a diagram illustrating a post-conversion database.

FIG. 9 is a block diagram illustrating a vehicle data management system.

DETAILED DESCRIPTION

Embodiments of the present disclosure will be described hereinafterreferring to drawings. In the embodiments, a part that corresponds to amatter described in a preceding embodiment may be assigned with the samereference numeral, and redundant explanation for the part may beomitted. When only a part of a configuration is described in anembodiment, another preceding embodiment may be applied to the otherparts of the configuration. The parts may be combined even if it is notexplicitly described that the parts can be combined. The embodiments maybe partially combined even if it is not explicitly described that theembodiments can be combined, provided there is no harm in thecombination.

First Embodiment

Hereinafter, a first embodiment of the present disclosure will bedescribed with reference to the drawings. A vehicle data managementsystem 1 of the present embodiment includes multiple data collectiondevices 2 and a vehicle data management device 3, as shown in FIG. 1.

The data collection device 2 is mounted on a vehicle and is configuredto perform data communication with the vehicle data management device 3through a wireless wide area network NW. The data collection device 2includes a control unit 11, a CAN communication unit 12, and acommunication unit 13, as shown in FIG. 2.

The control unit 11 is an electronic controller including as a maincomponent a microcontroller having a CPU, a ROM, a RAM, and the like.CAN is an abbreviation for Controller Area Network. CAN is a registeredtrademark.

The CAN communication unit 12 is configured to perform datacommunication with multiple in-vehicle components (such as electroniccontrollers and sensors) mounted on the vehicle in accordance with theCAN communication protocol. The communication unit 13 is configured toperform data communication with the vehicle data management device 3through the wireless wide area network NW.

The CAN communication unit 12 is connected with ECUs 111, 112, 113, ECUs121, 122, 123, and ECUs 131, 132, 133, for example. ECU is anabbreviation for Electronic Control Unit.

The ECUs 111, 112, 113 and the CAN communication unit 12 are connectedwith each other through a communication line 101 to perform datacommunication with each other by transmitting and receiving data inaccordance with CAN communication protocol.

The ECUs 121, 122, 123 and the CAN communication unit 12 are connectedwith each other through a communication line 102 to perform datacommunication with each other by transmitting and receiving data inaccordance with CAN communication protocol.

The ECUs 131, 132, 133 and the CAN communication unit 12 are connectedwith each other through a communication line 103 to perform datacommunication with each other by transmitting and receiving data inaccordance with CAN communication protocol.

The CAN network system is different for each vehicle manufacturer.However, the ECUs of the same system are arranged in the same domainnetwork. For example, in FIG. 2, a domain DM1 including thecommunication lines 101, 102 and the ECUs 111, 112, 113, 121, 122, 123is a domain for a powertrain system. A domain DM2 including thecommunication line 103 and the ECUs 131, 132, 133 is a domain for a bodysystem.

The data collection device 2 shown in FIG. 3 is mounted on a vehiclemanufactured by a vehicle manufacturer different from the vehiclemanufacturer of the vehicle on which the data collection device 2 ofFIG. 2 is mounted. The CAN communication unit 12 of the data collectiondevice 2 shown in FIG. 3 is connected with ECUs 211, 212, 213, ECUs 221,222, 223, ECUs 231, 232, 233, and ECUs 241, 242, 243.

The ECUs 211, 212, 213 and the CAN communication unit 12 are connectedwith each other through a communication line 201 to perform datacommunication with each other by transmitting and receiving data inaccordance with CAN communication protocol.

The ECUs 221, 222, 223 and the CAN communication unit 12 are connectedwith each other through a communication line 202 to perform datacommunication with each other by transmitting and receiving data inaccordance with CAN communication protocol.

The ECUs 231, 232, 233 and the CAN communication unit 12 are connectedwith each other through a communication line 203 to perform datacommunication with each other by transmitting and receiving data inaccordance with CAN communication protocol.

The ECUs 241, 242, 243 and the CAN communication unit 12 are connectedwith each other through a communication line 204 to perform datacommunication with each other by transmitting and receiving data inaccordance with CAN communication protocol.

A domain DM11 including the communication line 201 and the ECUs 211,212, 213 is a domain for the powertrain system. A domain DM12 includingthe communication line 202 and the ECUs 221, 222, 223 is a domain forthe body system.

Since the ECUs of the same system are arranged in the network for thesame system, the differences between the vehicle manufacturers can beabsorbed on the domain level. The vehicle data management device 3includes a control unit 31, a communication unit 32, and a storage unit33 as shown in FIG. 4.

The control unit 31 is an electronic controller including as a maincomponent a microcontroller having a CPU 41, a ROM 42, a RAM 43, and thelike. Various functions of the microcontroller are implemented byfunctioning the CPU 41 to execute program codes stored in anon-transitory tangible storage medium. In this example, the ROM 42corresponds to a non-transitory tangible storage medium that stores aprogram. In addition, by executing this program, a method correspondingto the program is executed. Note that a part or all of the functions tobe executed by the CPU 41 may be configured as hardware circuitry by oneor multiple ICs or the like. The number of microcontrollers configuringthe control unit 31 may be one or multiple.

The ROM 42 stores a conversion map 42 a used for a data conversionprocess described later. The communication unit 32 is configured toperform data communication with multiple data collection devices 2through the wireless wide area network NW.

The storage unit 33 is a memory device for storing various data. Thestorage unit 33 stores the pre-conversion database 33 a and thepost-conversion database 33 b. The pre-conversion database 33 a consistsof vehicle data acquired from multiple data collection devices 2 throughthe wireless wide area network NW.

The post-conversion database 33 b is obtained by converting the vehicledata in the pre-conversion database by the data conversion processdescribed later. The control unit 31 is connected with an analysisdevice 4 configured to analyze the data that the vehicle data managementdevice 3 collected from the data collection devices 2.

A CAN frame consists of a start-of-frame, arbitration field, controlfield, data field, CRC field, ACK field and end-of-frame, as shown inFIG. 5. The arbitration field consists of an 11-bits or 29-bitsidentifier (or ID) and a 1-bit RTR bit.

The 11-bits identifier used in CAN communication is called CAN ID. TheCAN ID is preset based on contents of data of the CAN frame, the senderof the CAN frame, the destination of the CAN frame, and the like.

The data field includes 8-bits (i.e. 1-byte) first data, second data,third data, fourth data, fifth data, sixth data, seventh data, andeighth data.

The pre-conversion database 33 a stores the CAN data in association witha vehicle ID, time, latitude, longitude, system, and CAN ID as shown inFIG. 6. The pre-conversion database 33 a has a matrix structure. In thepre-conversion database 33 a, the CAN data with earlier reception timehas smaller row number i.

The CAN data constitutes the data field of the CAN frame. That is, theCAN data is the first to eighth data described above. The vehicle ID isan identification number specified by a model and a model year of thevehicle that transmitted the corresponding CAN frame. For example, “012”shown in FIG. 6 is the vehicle ID of the vehicle equipped with the datacollection device 2 shown in FIG. 2. Further, “890” shown in FIG. 6 isthe vehicle ID of the vehicle equipped with the data collection device 2shown in FIG. 3.

The time, the latitude, and the longitude are those when thecorresponding CAN frame is transmitted. The system is an information foridentifying the CAN network in the vehicle that transmitted thecorresponding CAN frame. For example, “CAN1” shown in FIG. 6 indicatesthe CAN network including the communication line 101 and the ECUs 111,112, 113 shown in FIG. 2. “CAN2” shown in FIG. 6 indicates the CANnetwork including the communication line 102 and the ECUs 121, 122, 123shown in FIG. 2. “CANa” shown in FIG. 6 indicates the CAN networkincluding the communication line 201 and the ECUs 211, 212, 213 shown inFIG. 3. “CANb” shown in FIG. 6 indicates the CAN network including thecommunication line 202 and the ECUs 221, 222, 223 shown in FIG. 3.

The CAN ID is a CAN ID of the corresponding CAN frame. Next, the dataconversion process executed by the control unit 31 of the vehicle datamanagement device 3 will be described. The data conversion process isexecuted repeatedly during the operation of the vehicle data managementdevice 3.

When the data conversion process is started, the CPU 41 of the controlunit 31 assigns 1 to a row number indicator value i of RAM 43 in S10, asshown in FIG. 7. In S20, the CPU 41 sets a maximum row number n of RAM43. Specifically, the CPU 41 gets the number of the rows of the matrixof the pre-conversion database 33 a and assigns the number of the rowsto the maximum row number n of the RAM 43.

In S30, the CPU 41 gets from the pre-conversion database 33 a thevehicle ID in the row corresponding to the row number indicator value i.For example, in FIG. 6, when the row number indictor value i is 2, thevehicle ID is “012”.

Next, in S40, the CPU 41 refers to the conversion map 42 a to convertthe system in the row corresponding to the row number indicator value iin the pre-conversion database 33 a to the domain. The conversion map 42a stores a domain identification information that indicates acorrespondence between the CAN ID and the domain for each of the vehicleIDs. For example, when the vehicle ID is “012”, the CAN ID of “123” isassociated with the powertrain, the CAN ID of “7FE” is associated withthe powertrain, and the CAN ID of “311” is associated with the body.When the vehicle ID is “890”, the CAN ID of “233” is associated with thepowertrain, the CAN ID of “4a1” is associated with the powertrain, andthe CAN ID of “68E” is associated with the body.

In S50, the CPU 41 refers to the conversion map 42 a to convert the CANID in the row corresponding to the row number indicator value i in thepre-conversion database 33 a to the control label. Further, the CPU 41refers to the conversion map 42 a to convert the CAN data in the rowcorresponding to the row number indicator value i in the pre-conversiondatabase 33 a to the vehicle information.

The conversion map 42 a stores one or more combinations of the controllabel, a bit assignment, and a conversion information for each vehicleID. For example, when the vehicle ID is “012”, a bit assignment whoseCAN ID is “123” and data position is “Byte 1, Bit 0, Len 8”, and aconversion information expressed by a conversion formula for convertingthe CAN data into the engine speed are associated with the control labelof the engine speed. “Byte 1, Bit 0, Len 8” corresponds to the bits 0-7of the first data in the data field of the CAN frame.

When the vehicle ID is “012”, a bit assignment whose CAN ID is “123” anddata position is “Byte 2, Bit 0, Len 3”, and a conversion informationexpressed by a conversion formula for converting the CAN data into theaccelerator open degree are associated with the control label of theaccelerator open degree. “Byte 2, Bit 0, Len 3” corresponds to the bits0-2 of the second data in the data field of the CAN frame.

When the vehicle ID is “012”, a bit assignment whose CAN ID is “7FE” anddata position is “Bite 2, Bit 0, Len 2”, and a conversion informationrepresented by the correspondence between the CAN data and P, R, D, S, Brange or the like are associated with the control label of the shiftposition. “Byte 2, Bit 0, Len 3” corresponds to the bits 0, 1, 3 of thesecond data in the data field of the CAN frame.

When the vehicle ID is “012”, a bit assignment and a conversioninformation represented by a correspondence between the CAN data and thehigh beam, the low beam and the like are associated with the controllabel of the headlight.

When the vehicle ID is “890”, a bit assignment whose CAN ID is “233” anddata position is “Byte 2, Bit 0, Len 8”, and a conversion informationexpressed by a formula for converting the CAN data into the engine speedare associated with the control label of the engine speed. “Byte 2, Bit0, Len 8” corresponds to the bits 0-7 of the second data in the datafield of the CAN frame.

When the vehicle ID is “890”, a bit assignment and a conversioninformation represented by a correspondence between the CAN data and P,R, D, S, B ranges are associated with the control label of the shiftposition.

When the vehicle ID is “890”, a bit assignment and a conversioninformation represented by a correspondence between the CAN data and thehigh beam, the low beam and the like are associated with the controllabel of the headlight.

In S60, the CPU 41 determines whether the value stored in the row numberindicator value i is equal to or greater than the value stored in themaximum row number n. When the value stored in the row number indicatorvalue i is smaller than the value stored in the maximum row number n,the CPU 41 increments the row number indicator value i by 1 in S70, andthe process returns to S30.

In contrast, when the value stored in the row number indicator value iis equal to or greater than the value stored in the maximum row numbern, the CPU 41 stores, in the post-conversion database 33 b, theconverted data which is stored in the first to nth rows of thepre-conversion database 33 a, the vehicle ID, the time, the latitude,and the longitude corresponding to the converted data such that the dataconverted earlier has smaller row number in S80.

In S90, the CPU 41 deletes the data in the first to nth rows of thepre-conversion database 33 a (i.e. the converted data) from thepre-conversion database 33 a, and thus the data conversion process ends.

The post-conversion database 33 b is shown in FIG. 8, which can beobtained by converting the pre-conversion database 33 a shown in FIG. 6through the data conversion process. As shown in FIG. 8, thepost-conversion database 33 b stores the vehicle information, and eachvehicle information is associated with the vehicle ID, the time,latitude, longitude, system, and control label. The post-conversiondatabase 33 b has a matrix structure. In FIG. 8, “4567 rpm”, “50%”, and“3333 rpm” are physical values, and “D-range”, “high beam”, and “lowbeam” are type values.

As described above, the vehicle data management device 3 includes thecommunication unit 32 and the control unit 31. The communication unit 32is configured to acquire, from the data collection devices 2 mounted onthe vehicles respectively, the vehicle ID which is set based on at leastthe vehicle model, and the CAN data indicative of vehicle informationwhich is contained in the CAN frame transmitted and received in the CANnetwork of the vehicle.

The control unit 31 is configured to convert the CAN data into thecontrol label and a management value for each vehicle ID based on theconversion map 42 a which contains at least one of the bit assignmentfor identifying the control label of the CAN data and the conversioninformation for converting the CAN data into the physical value or thetype value (hereinafter, referred to as the management value).

The bit assignment is an information indicative of a position of the CANdata in the CAN frame. The conversion information is set for each bitassignment and is indicative of a correspondence between the CAN dataand the management value.

Accordingly, the vehicle data management device 3 is configured toidentify the control label of each CAN data based on the bit assignmentof the conversion map 42 a. For example, when (i) the vehicle ID is“012”, (ii) the CAN ID of the bit assignment is “123”, and (iii) thedata position of the bit assignment is “Byte 1, Bit 0, Len 8”, thecontrol label is “engine speed”. Further, when (i) the vehicle ID is“890”, (ii) the CAN ID of the bit assignment is “233”, and (iii) thedata position of the bit assignment is “Byte 2, Bit 0, Len 8”, thecontrol label is “engine speed”. According to the vehicle datamanagement device 3, the same control label of “engine speed” can beassigned to the CAN data whose vehicle IDs and CAN IDs are differentfrom each other.

Accordingly, the vehicle data management device 3 is configured toclassify the CAN data with different vehicle IDs into the same group bythe control label. Accordingly, the vehicle data management device 3 caneasily manage the database (i.e. the post-conversion database 33 b)consisting of vehicle information acquired from multiple data collectiondevices 2.

CAN data contains the CAN ID indicative of the CAN network used fortransmitting and receiving the CAN frame in which the CAN data isstored. The conversion map 42 a contains the domain identificationinformation indicative of the correspondence between the CAN ID and thedomain of the vehicle. The control unit 31 is configured to identify thedomain corresponding to the management value based on the domainidentification information of the conversion map 42 a. Accordingly, thevehicle data management device 3 is configured to classify the CAN datawith different vehicle IDs into the same group based on the domain.Accordingly, the vehicle data management device 3 can easily manage thedatabase (i.e. the post-conversion database 33 b) consisting of vehicleinformation acquired from multiple data collection devices 2.

The control unit 31 stores at least the converted control label andmanagement value. According to the vehicle data management device 3, theanalysis device 4 can utilize the database (i.e. the post-conversiondatabase 33 b) consisting of the vehicle information acquired frommultiple data collection devices 2. Since the CAN data with differentvehicle IDs stored in the post-conversion database 33 b can beclassified based on the control label and the domain, the analysisdevice 4 can easily extract information required for analysis using thecontrol label and the domain.

In the above-described embodiment, the data collection device 2corresponds to an in-vehicle device, the communication unit 32corresponds to a data acquisition unit, and the process in S50corresponds to a data conversion unit. The vehicle ID corresponds to avehicle identification information, the CAN data corresponds to a firstdata, the control label corresponds to a label, the management valuecorresponds to a second data, and the bit assignment corresponds to alabel identification information.

The CAN ID corresponds to a network identification information, theprocess in S40 corresponds to a domain identification unit, and theprocess in S80 corresponds to a post-conversion data storage unit.

Second Embodiment

Hereinafter, a second embodiment of the present disclosure will bedescribed with reference to the drawings. Note that in the secondembodiment, portions different from the first embodiment is described.The same reference numerals are given to common components.

As shown in FIG. 9, the vehicle data management system 1 of the secondembodiment includes a first manufacturer management server 301, a secondmanufacturer management server 302, a third manufacturer managementserver 303, and a fourth manufacturer management server 304 differentlyfrom the first embodiment.

The first manufacturer management server 301, the second manufacturermanagement server 302, the third manufacturer management server 303, andthe fourth manufacturer management server 304 perform data communicationwith the vehicle data management device 3 through the wireless wide areanetwork NW.

The first manufacturer management server 301, the second manufacturermanagement server 302, the third manufacturer management server 303, andthe fourth manufacturer management server 304 are servers managed by afirst vehicle manufacturer, a second vehicle manufacturer, a thirdvehicle manufacturer, and a fourth vehicle manufacturer, respectively.

The first manufacturer management server 301, the second manufacturermanagement server 302, the third manufacturer management server 303, andthe fourth manufacturer management server 304 store a first conversionmap 311, a second conversion map 312, a third conversion map 313, and afourth conversion map 314, respectively.

The first manufacturer management server 301, the second manufacturermanagement server 302, the third manufacturer management server 303, andthe fourth manufacturer management server 304 transmit the firstconversion map 311, the second conversion map 312, the third conversionmap 313, and the fourth conversion map 314 to the vehicle datamanagement device 3, respectively.

The vehicle data management device 3 stores the received firstconversion map 311, the second conversion map 312, the third conversionmap 313, and the fourth conversion map 314 in the storage unit 33. Theconversion maps 311, 312, 313, 314 are maps each of which contains oneor more combinations of the control label, the bit assignment, and theconversion information for each vehicle ID of the vehicle manufacturedby the first to fourth vehicle manufacturers, respectively.

The vehicle data management device 3 is configured to convert the systemof the pre-conversion database 33 a by referring to the first to fourthconversion maps 311, 312, 313, 314 stored in the storage unit 33. Thevehicle data management device 3 is configured to respectively convertthe CAN ID and the CAN data in the pre-conversion database 33 a into thecontrol label and the vehicle information by referring to the first tofourth conversion maps 311, 312, 313, 314 stored in the storage unit 33.

The vehicle data management system 1 as described above includes thevehicle data management device 3, the first manufacturer managementserver 301, the second manufacturer management server 302, the thirdmanufacturer management server 303, the fourth manufacturer managementserver 304, and the analysis device 4.

The vehicle data management device 3 includes the communication unit 32and the control unit 31. The communication unit 32 is configured toacquire, from the data collection devices 2 mounted on the vehiclesrespectively, the vehicle ID which is set based on at least the vehiclemodel, and the CAN data indicative of vehicle information which iscontained in the CAN frame transmitted and received in the CAN networkof the vehicle.

The control unit 31 is configured to convert the CAN data into thecontrol label and a management value for each vehicle ID based on thefirst to fourth conversion maps 311, 312, 313, 314 each of whichcontains at least one of the bit assignment for identifying the controllabel of the CAN data and the conversion information for converting theCAN data into the physical value or the type value (hereinafter,referred to as the management value).

The first to fourth manufacturer management servers 301, 302, 303, 304store the first to fourth conversion maps 311, 312, 313, 314,respectively. The analysis device 4 is configured to perform theanalysis using the control label and the management value converted bythe vehicle data management device 3. The first to fourth manufacturermanagement servers 301, 302, 303, 304 and the vehicle data managementdevice 3 are connected to perform data communication.

The vehicle data management system 1 is a system including the vehicledata management device 3, and the same effects as the vehicle datamanagement device 3 of the first embodiment can be obtained. In theembodiment described above, the first to fourth manufacturer managementservers 301, 302, 303, 304 correspond to a map storage device.

As described above, the embodiments of the present disclosure aredescribed, but the present disclosure is not limited to the aboveembodiments, and can be implemented with various modifications.

MODIFIED EXAMPLE

In the above-described embodiments, “engine speed”, “accelerator opendegree”, “shift position”, and “headlight” are referred to as thecontrol labels which are labels of data directly related to the vehiclecontrol. However, the data managed by the vehicle data management device3 is not limited to the data directly related to the vehicle control,and other data may be managed as long as the data can be acquired by thevehicle such as “state of driver”. Accordingly, the label used in thepost-conversion database 33 b is not limited to the control label andmay be an occupant label, for example.

The control unit 31 and method described in the present disclosure maybe implemented by a special purpose computer which is configured with amemory and a processor programmed to execute one or more particularfunctions embodied in computer programs of the memory. Alternatively,the control unit 31 described in the present disclosure and the methodthereof may be realized by a dedicated computer configured as aprocessor with one or more dedicated hardware logic circuits.Alternatively, the control unit 31 and method described in the presentdisclosure may be realized by one or more dedicated computer, which isconfigured as a combination of a processor and a memory, which areprogrammed to perform one or more functions, and a processor which isconfigured with one or more hardware logic circuits. Further, thecomputer program may be stored in a computer-readable non-transitorytangible storage medium as instructions to be executed by a computer.The technique for realizing the functions of each unit included in thecontrol unit 31 does not necessarily need to include software, and allthe functions may be realized using one or a plurality of hardwarecircuits.

The multiple functions of one component in the above embodiment may berealized by multiple components, or a function of one component may berealized by the multiple components. In addition, multiple functions ofmultiple components may be realized by one component, or a singlefunction realized by multiple components may be realized by onecomponent. Moreover, part of the configuration of the above-describedembodiment may be omitted. Further, at least part of the configurationof the above-described embodiment may be added to or replaced with theconfiguration of another embodiment described above.

In addition to the vehicle data management device 3 described above,various features such as a system having the vehicle data managementdevice 3 as a component, a program for making the computer function asthe vehicle data management device 3, a non-transitory tangible storagemedium such as a semiconductor memory in which the program is stored,and a method of converting data may provide to realize the presentdisclosure.

Additional advantages and modifications will readily occur to thoseskilled in the art. The disclosure in its broader terms is therefore notlimited to the specific details, representative apparatus, andillustrative examples shown and described.

What is claimed is:
 1. A vehicle data management device comprising: adata acquisition unit configured to acquire, from each of a plurality ofin-vehicle devices mounted on a corresponding vehicle of a plurality ofvehicles, a vehicle identification information that is set based on atleast a model of the vehicle, and a first data that is contained in acommunication frame transmitted and received in an in-vehicle network ofthe vehicle and is indicative of a vehicle information relating to thevehicle, a data conversion unit configured to convert the first datainto a label and a second data that is a physical value or a type valuebased on a conversion map that contains a label identificationinformation for identifying the label corresponding to the first data,and a conversion information for converting the first data into thesecond data, wherein the conversion map contains at least one labelidentification information and at least one conversion information foreach vehicle identification information.
 2. The vehicle data managementdevice according to claim 1, wherein the label identificationinformation is indicative of a position in the communication frame wherethe first data is stored.
 3. The vehicle data management deviceaccording to claim 1, wherein the conversion information is set for eachlabel identification information and is indicative of a correspondencerelationship between the first data and the second data.
 4. The vehicledata management device according to claim 1, wherein the first datacontains a network identification information for identifying acommunication network used for data transmission of the communicationframe containing the first data, the conversion map contains a domainidentification information indicative of a correspondence relationshipbetween the network identification information and a domain of thevehicle, and the vehicle data management device further comprises: adomain identification unit configured to identify the domaincorresponding to the second data based on the domain identificationinformation of the conversion map.
 5. The vehicle data management deviceaccording to claim 1, further comprising: a post-conversion data storageunit configured to store at least the label and the second dataconverted by the data conversion unit.
 6. A vehicle data managementsystem comprising: a vehicle data management device; at least one mapstorage device; and an analysis device, wherein the vehicle datamanagement device includes: a data acquisition unit configured toacquire, from each of a plurality of in-vehicle devices mounted on acorresponding vehicle of a plurality of vehicles, a vehicleidentification information that is set based on at least a model of thevehicle, and a first data that is contained in a communication frametransmitted and received in an in-vehicle network of the vehicle and isindicative of a vehicle information relating to the vehicle; and a dataconversion unit configured to convert the first data into a label and asecond data that is a physical value or a type value based on aconversion map that contains a label identification information foridentifying the label corresponding to the first data, and a conversioninformation for converting the first data into the second data, whereinthe conversion map contains at least one label identificationinformation and at least one conversion information for each vehicleidentification information, the at least one map storage device storesthe conversion map, the analysis deice is configured to analyze thevehicle using the label and the second data converted by the vehicledata management device, and the at least one map storage device and thevehicle data management device are communicably connected with eachother.
 7. A method of managing vehicle data, the method comprising:acquiring a vehicle identification information and a first data fromeach of a plurality of in-vehicle devices mounted on a correspondingvehicle of a plurality of vehicles, the vehicle identificationinformation being set based on at least a model of the vehicle, thefirst data being indicative of a vehicle information relating to thevehicle and being contained in a communication frame transmitted andreceived in an in-vehicle network of the vehicle; and converting thefirst data into a label and a second data that is a physical value or atype value based on a conversion map that contains a labelidentification information for identifying the label corresponding tothe first data and a conversion information for converting the firstdata into the second data, the conversion map containing at least onelabel identification information and at least one conversion informationfor each vehicle identification information.